Skip to content

Conversation

patrickbirch
Copy link
Collaborator

…ver in MySQL 8.4.5

On branch ps-10137-8.4
modified: docs/audit-log-filter-restrictions.md

…ver in MySQL 8.4.5

 On branch ps-10137-8.4
	modified:   docs/audit-log-filter-restrictions.md
* Hold the application or user responsible for aggregating all the data from
each server used in the cluster if used with a cluster.

* Each server must have its own audit log filter rules. If you do not set up the rules on the replica server, that server does not record the corresponding entries in the audit log. This design requires that the audit log configuration be performed separately for each server.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would also add

As by default the content of the 'mysql.audit_log_filter' and 'mysql.audit_log_user' tables may be replicated from source to replica and may affect audit log rules created on the replica, it is recommended to configure replication in such a way that the changes in these tables are simply ignored.
Please notice that just changing the content of these table (via replication channel) is not enough to automatically make changes to in-memory data structures in the 'audit_log_filter' component that store information about active audit log filtering rules. However, this may happen after component reloading / server restart or manually calling 'audit_log_filter_flush()'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants